-
Notifications
You must be signed in to change notification settings - Fork 152
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Delete platform-specific specs from configv1 #5300
Conversation
Signed-off-by: Shinnosuke Sawada-Dazai <[email protected]>
@@ -104,30 +105,10 @@ func (c *Config) init(kind Kind, apiVersion string) error { | |||
c.APIVersion = apiVersion | |||
|
|||
switch kind { | |||
case KindApplication: | |||
case KindApplication, KindKubernetesApp, KindTerraformApp, KindCloudRunApp, KindLambdaApp, KindECSApp: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
To have backward compatibility, we treat them as the same as the KindApplication.
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #5300 +/- ##
==========================================
+ Coverage 25.14% 25.16% +0.01%
==========================================
Files 449 444 -5
Lines 47642 47504 -138
==========================================
- Hits 11980 11954 -26
+ Misses 34717 34606 -111
+ Partials 945 944 -1 ☔ View full report in Codecov by Sentry. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM 👋
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
What this PR does:
as title
Why we need it:
We move platform-specific config to plugins, so we don't want these at the configv1 package.
I copied them on #5237, but I realized it was not a good way to copy all of them, so I removed some parts on this PR.
Which issue(s) this PR fixes:
Part of #4980
Does this PR introduce a user-facing change?: